Method, apparatus, and system for obtaining network slice

ABSTRACT

This application discloses a method for obtaining a network slice. The method includes: receiving, by a control device, a slice request sent by a user, where the slice request includes an identifier, and the identifier is used to identify isolation information of a slice requested by the user; obtaining, by the control device, a network slice based on the identifier and a resource topology, where the resource topology is used to describe a network topology and isolation information of N elements in the network topology, the N elements include at least one of a node and a link, N is an integer greater than or equal to 1, and the network slice includes a node and a link that are required for implementing the slice.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/137,405, filed on Dec. 30, 2020, which is a continuation ofInternational Application No. PCT/CN2019/076217, filed on Feb. 27, 2019,which claims priority to Chinese Patent Application No. 201810702468.3,filed on Jun. 30, 2018. All of the aforementioned applications arehereby incorporated by reference in their entireties.

TECHNICAL FIELD

This application relates to the communications field, and in particular,to a method, an apparatus, and a system for obtaining a network slice.

BACKGROUND

FIG. 1 is a schematic diagram of a network scenario of obtaining anetwork slice. In the scenario shown in FIG. 1 , a control deviceincludes an orchestrator, a controller of a network A, and a controllerof a network B. The controller 1 of the network A communicates with anode included in the network A, to obtain topology information of thenetwork A. The network A includes a node A, a node B, a node C, and anode D. The controller 1 sends the obtained topology information of thenetwork A to the orchestrator. The controller 2 of the network Bcommunicates with a node included in the network B, to obtain topologyinformation of the network B. The network B includes a node E, a node F,a node G, and a node H. The controller 2 sends the obtained topologyinformation of the network B to the orchestrator. The orchestrator mayobtain information about a topology between the node A and the node Hbased on the topology information of the network A and the topologyinformation of the network B. The information about the topologyincludes node information and link information. The node informationincludes a node identifier (ID), a node terminal point (Node-TP), and anode location. The Node-TP is a physical port of a node or a logicalport of a node. The link information includes a link ID, a source nodeID, a source link TP (source-TP), a destination node ID, and adestination link TP (dest-TP). The source node ID is used to identify asource node of a link. The source link TP is used to identify a TP ofthe source node of the link. The destination node ID is used to identifya destination node of the link. The destination link TP is used toidentify a TP of the destination node of the link. Herein, only acontrol device including an orchestrator and a plurality of controllersis used as an example for description. In practice, the foregoingprocessing may alternatively be performed by a control device of anothertype that does not have an orchestrator, and the control device ofanother type may directly manage the networks A and B.

A process of communication between a node and any one of the foregoingcontrol devices does not include exchanging node isolation informationor link isolation information, and the control device does not have acapability of processing an isolation function. Correspondingly, thetopology information obtained by the control device does not includeisolation information. In this case, when a service deployed in anetwork managed and controlled by the control device needs to implementa specific isolation capability, the control device cannot provide afine-grained management and control service, resulting in impact onservice running to some extent. For example, a network slice service isdescribed below.

The orchestrator receives a slice request sent by a user. The slicerequest includes a parameter related to a service-level agreement (SLA).The parameter related to the SLA is used to indicate a service instancecorresponding to a network slice instance (NSI). The orchestratorcalculates, based on the slice request and the information about thetopology between the node A and the node H, a network resource thatmeets the slice request, to form the NSI. In the scenario shown in FIG.1 , the orchestrator can obtain, based on only the SLA in the slicerequest of the user, that both a path A-B-C-E-G-H and a path A-B-D-F-G-Hcan meet the SLA. When a service that the slice request requests todeploy needs to implement a specific isolation capability, theorchestrator cannot select, from the path A-B-C-E-G-H and the pathA-B-D-F-G-H, a path that supports the specific isolation capability.Consequently, a corresponding network resource cannot be allocated tothe service corresponding to the slice request, and the isolationcapability required by the service cannot be implemented.

SUMMARY

Embodiments of this application provide a method, an apparatus, and asystem for obtaining a network slice, to create a network slice thatmatches an isolation capability required by a service, therebyimplementing the isolation capability required by the service.

According to a first aspect, a method for obtaining a network slice isprovided, where the method includes: receiving, by a control device, aslice request sent by a user, where the slice request includes anidentifier, and the identifier is used to identify an isolation level ofa slice requested by the user; obtaining, by the control device, anisolation type of the slice based on the identifier; and creating, bythe control device, a network slice based on the isolation type of theslice and a resource topology, where the resource topology is used todescribe a network topology and isolation capabilities of N elements inthe network topology, the N elements include at least one of a node anda link, N is an integer greater than or equal to 1, and the networkslice includes a node and a link that are required for implementing theslice.

In the foregoing method, the control device can determine the isolationtype of the slice based on the slice request, and thereby select, fromthe resource topology based on the isolation type, an element forimplementing the slice, so that an isolation capability of the selectedelement matches the isolation type. In this way, the control devicecreates the network slice by using the element, thereby implementing theisolation capability required by the service.

In a design of the first aspect, the N elements include a first node, asecond node, and a link between the first node and the second node, andthe method further includes: obtaining, by the control device, firstresource information from the first node according to an isolationpolicy, where the first resource information includes isolationinformation provided by the first node and a topology of the first node;obtaining, by the control device, second resource information from thesecond node according to an isolation policy, where the second resourceinformation includes isolation information provided by the second nodeand a topology of the second node; and generating, by the controldevice, a resource topology based on the first resource information andthe second resource information, where the resource topology is used todescribe the network topology, an isolation capability of the firstnode, an isolation capability of the second node, and an isolationcapability of the link between the first node and the second node, andthe network topology is a topology between the first node and the secondnode.

In the foregoing design, the control device generates, based on theisolation capabilities of the elements in a network, the resourcetopology that can support some isolation capabilities. In this way, whencreating the network slice, the control device may generate, based onthe isolation capability supported by the resource topology, a slicehaving the isolation capability, and the slice can implement theisolation capability required by the service. The control device mayflexibly obtain configuration data according to the isolation policy,and thereby obtain the resource topology having a specific isolationcapability.

In a design of the first aspect, the obtaining, by the control device,first resource information from the first node according to an isolationpolicy includes: generating, by the control device, first configurationdata according to the isolation policy, where the first configurationdata is used to describe the isolation capability of the first node;sending, by the control device, the first configuration data to thefirst node; and receiving, by the control device, the first resourceinformation sent by the first node, where the first resource informationincludes the isolation information provided by the first node and thetopology of the first node, and the topology of the first node is usedto describe the first node and a link on which the first node islocated.

In a design of the first aspect, the obtaining, by the control device,second resource information from the second node according to anisolation policy includes: generating, by the control device, secondconfiguration data according to the isolation policy, where the secondconfiguration data is used to describe the isolation capability of thesecond node; sending, by the control device, the second configurationdata to the second node; and receiving, by the control device, thesecond resource information sent by the second node, where the secondresource information includes the isolation information provided by thesecond node and the topology of the second node, and the topology of thesecond node is used to describe the second node and a link on which thesecond node is located.

In a design of the first aspect, the generating, by the control device,first configuration data according to an isolation policy includes:obtaining, by the control device, the isolation capability of the firstnode according to the isolation policy, where the isolation capabilityof the first node includes isolation capabilities of the first node andthe link on which the first node is located; and generating, by thecontrol device based on the isolation capability of the first node and adata model, the first configuration data described by using the datamodel.

In a design of the first aspect, the generating, by the control device,second configuration data according to an isolation policy includes:obtaining, by the control device, the isolation capability of the secondnode according to the isolation policy, where the isolation capabilityof the second node includes isolation capabilities of the second nodeand the link on which the second node is located; and generating, by thecontrol device based on the isolation capability of the second node andthe data model, the second configuration data described by using thedata model.

In a design of the first aspect, the generating, by the control device,a resource topology based on the first resource information and thesecond resource information includes: determining, by the controldevice, a first isolation type based on the isolation informationprovided by the first node and the isolation information provided by thesecond node; and obtaining, by the control device based on the firstisolation type and the network topology, a first resource topologymatching the first isolation type, where an isolation capability of anode included in the first resource topology is the first isolationtype, and an isolation capability of a link included in the firstresource topology is the first isolation type.

In a design of the first aspect, the generating, by the control device,a resource topology based on the first resource information and thesecond resource information further includes: determining, by thecontrol device, a second isolation type based on the isolationinformation provided by the first node and the isolation informationprovided by the second node; and obtaining, by the control device basedon the second isolation type and the network topology, a second resourcetopology matching the second isolation type, where an isolationcapability of a node included in the second resource topology is thesecond isolation type, and an isolation capability of a link included inthe second resource topology is the second isolation type.

In the foregoing design, the control device may generate, based on thedifferent isolation types, the sub-resource topologies that match theisolation types. The control device further generates the resourcetopology based on the sub-resource topologies that match the isolationtypes.

In a design of the first aspect, the first isolation type isfine-grained physical isolation, coarse-grained physical isolation, orlogical isolation, the second isolation type is fine-grained physicalisolation, coarse-grained physical isolation, or logical isolation, andthe second isolation type is different from the first isolation type.

In a design of the first aspect, the first isolation type is networkisolation, link isolation, or node isolation, the second isolation typeis network isolation, node physical isolation, or link isolation, andthe second isolation type is different from the first isolation type.

In a design of the first aspect, the creating, by the control device, anetwork slice based on the isolation type of the slice and a resourcetopology includes: selecting, by the control device from the resourcetopology based on the isolation type of the slice, a sub-resourcetopology matching the isolation type of the slice, where an isolationcapability of a node included in the sub-resource topology is theisolation type of the slice, and an isolation capability of a linkincluded in the sub-resource topology is the isolation type of theslice; and storing, by the control device, a correspondence between thesub-resource topology and the identifier.

In a design of the first aspect, the creating, by the control device, anetwork slice based on the isolation type of the slice and a resourcetopology further includes: obtaining, by the control device based on theslice request, service information corresponding to the slice;obtaining, by the control device, an ingress terminal point TP and anegress TP of a third node based on the sub-resource topology, where anisolation capability of the ingress TP is an isolation capability of theslice, an isolation capability of the egress TP is the isolationcapability of the slice, the isolation capability of the ingress TPsupports the isolation capability of the node included in thesub-resource topology and the isolation capability of the link includedin the sub-resource topology, and the isolation capability of the egressTP supports the isolation capability of the node included in thesub-resource topology and the isolation capability of the link includedin the sub-resource topology; and sending, by the control device to thethird node, a correspondence including the service information, theingress TP, and the egress TP.

In a design of the first aspect, after the creating a network slice, themethod further includes: obtaining, by the control device, updatedisolation information from the first node, where the updated isolationinformation is used to describe a newly added isolation capability inthe first node or an invalid isolation capability in the first node; andobtaining, by the control device, an updated resource topology based onthe updated isolation information and the resource topology, where theupdated resource topology is used to describe the network topology, anupdated isolation capability of the first node, the isolation capabilityof the second node, and an updated isolation capability of the linkbetween the first node and the second node.

In the foregoing design, the control device may update the generatedresource topology based on the updated isolation information activelyreported by the first node, to meet an isolation capability required bya subsequent service.

In a design of the first aspect, the isolation level is a user level, aservice level, a tunnel level, a system level, a slot level, awavelength level, a port level, a device level, or a network level, andthe isolation capability is an isolation function that is of an elementand that corresponds to the isolation level. The device level can befurther divided into forwarding isolation, cross-connection isolation,and system isolation.

According to a second aspect, a method for obtaining a resource topologyis provided, where the method includes: obtaining, by a control device,first resource information from a first node according to an isolationpolicy, where the first resource information includes isolationinformation provided by the first node and a topology of the first node;obtaining, by the control device, second resource information from asecond node according to an isolation policy, where the second resourceinformation includes isolation information provided by the second nodeand a topology of the second node; and generating, by the controldevice, a resource topology based on the first resource information andthe second resource information, where the resource topology is used todescribe a network topology, an isolation capability of the first node,an isolation capability of the second node, and an isolation capabilityof a link between the first node and the second node, and the networktopology is a topology between the first node and the second node.

In the foregoing method, the control device generates, based on theisolation capabilities of the elements in a network, the resourcetopology that can support some isolation capabilities. In this way, whencreating the network slice, the control device may generate, based onthe isolation capability supported by the resource topology, a slicehaving the isolation capability, and the slice can implement theisolation capability required by the service. The control device mayflexibly obtain configuration data according to the isolation policy,and thereby obtain the resource topology having a specific isolationcapability.

In a design of the second aspect, the obtaining, by the control device,first resource information from the first node according to an isolationpolicy includes: generating, by the control device, first configurationdata according to the isolation policy, where the first configurationdata is used to describe the isolation capability of the first node;sending, by the control device, the first configuration data to thefirst node; and receiving, by the control device, the first resourceinformation sent by the first node, where the first resource informationincludes the isolation information provided by the first node and thetopology of the first node, and the topology of the first node is usedto describe the first node and a link on which the first node islocated.

In a design of the second aspect, the obtaining, by the control device,second resource information from the second node according to anisolation policy includes: generating, by the control device, secondconfiguration data according to the isolation policy, where the secondconfiguration data is used to describe the isolation capability of thesecond node; sending, by the control device, the second configurationdata to the second node; and receiving, by the control device, thesecond resource information sent by the second node, where the secondresource information includes the isolation information provided by thesecond node and the topology of the second node, and the topology of thesecond node is used to describe the second node and a link on which thesecond node is located.

In a design of the second aspect, the generating, by the control device,first configuration data according to an isolation policy includes:obtaining, by the control device, the isolation capability of the firstnode according to the isolation policy, where the isolation capabilityof the first node includes isolation capabilities of the first node andthe link on which the first node is located; and generating, by thecontrol device based on the isolation capability of the first node and adata model, the first configuration data described by using the datamodel.

In a design of the second aspect, the generating, by the control device,second configuration data according to an isolation policy includes:obtaining, by the control device, the isolation capability of the secondnode according to the isolation policy, where the isolation capabilityof the second node includes isolation capabilities of the second nodeand the link on which the second node is located; and generating, by thecontrol device based on the isolation capability of the second node andthe data model, the second configuration data described by using thedata model.

In a design of the second aspect, the generating, by the control device,a resource topology based on the first resource information and thesecond resource information includes: determining, by the controldevice, a first isolation type based on the isolation informationprovided by the first node and the isolation information provided by thesecond node; and obtaining, by the control device based on the firstisolation type and the network topology, a first resource topologymatching the first isolation type, where an isolation capability of anode included in the first resource topology is the first isolationtype, and an isolation capability of a link included in the firstresource topology is the first isolation type.

In a design of the second aspect, the generating, by the control device,a resource topology based on the first resource information and thesecond resource information further includes: determining, by thecontrol device, a second isolation type based on the isolationinformation provided by the first node and the isolation informationprovided by the second node; and obtaining, by the control device basedon the second isolation type and the network topology, a second resourcetopology matching the second isolation type, where an isolationcapability of a node included in the second resource topology is thesecond isolation type, and an isolation capability of a link included inthe second resource topology is the second isolation type.

In a design of the second aspect, the method further includes:obtaining, by the control device, updated isolation information from thefirst node, where the updated isolation information is used to describea newly added isolation capability in the first node or an invalidisolation capability in the first node; and obtaining, by the controldevice, an updated resource topology based on the updated isolationinformation and the resource topology, where the updated resourcetopology is used to describe the network topology, an updated isolationcapability of the first node, the isolation capability of the secondnode, and an updated isolation capability of the link between the firstnode and the second node.

In a design of the second aspect, the method further includes:receiving, by the control device, a slice request sent by a user, wherethe slice request includes an identifier, and the identifier is used toidentify an isolation level of a slice requested by the user; obtaining,by the control device, an isolation type of the slice based on theidentifier; and creating, by the control device, a network slice basedon the isolation type of the slice and the resource topology, where theresource topology is used to describe a network topology and isolationcapabilities of N elements in the network topology, the N elementsinclude at least one of a node and a link, N is an integer greater thanor equal to 1, and the network slice includes a node and a link that arerequired for implementing the slice.

According to a third aspect, a control device is provided, where thecontrol device includes a receiving unit, a first obtaining unit, and acreation unit. The receiving unit is configured to receive a slicerequest sent by a user, where the slice request includes an identifier,and the identifier is used to identify an isolation level of a slicerequested by the user; the first obtaining unit is configured to obtainan isolation type of the slice based on the identifier; and the creationunit is configured to create a network slice based on the isolation typeof the slice and a resource topology, where the resource topology isused to describe a network topology and isolation capabilities of Nelements in the network topology, the N elements include at least one ofa node and a link, N is an integer greater than or equal to 1, and thenetwork slice includes a node and a link that are required forimplementing the slice.

In a design of the third aspect, the N elements include a first node, asecond node, and a link between the first node and the second node; andthe control device further includes a second obtaining unit, a thirdobtaining unit, and a generating unit. The second obtaining unit isconfigured to obtain first resource information from the first nodeaccording to an isolation policy, where the first resource informationincludes isolation information provided by the first node and a topologyof the first node; the third obtaining unit is configured to obtainsecond resource information from the second node according to anisolation policy, where the second resource information includesisolation information provided by the second node and a topology of thesecond node; and the generating unit is configured to generate aresource topology based on the first resource information and the secondresource information, where the resource topology is used to describethe network topology, an isolation capability of the first node, anisolation capability of the second node, and an isolation capability ofthe link between the first node and the second node, and the networktopology is a topology between the first node and the second node.

In one or more designs of the third aspect, the units included in thecontrol device can implement any design of the first aspect. The controldevice in any one of the third aspect or the designs of the third aspectis an apparatus configured to obtain a network slice.

According to a fourth aspect, a control device is provided, where thecontrol device includes a first obtaining unit, a second obtaining unit,and a generating unit. The second obtaining unit is configured to obtainfirst resource information from a first node according to an isolationpolicy, where the first resource information includes isolationinformation provided by the first node and a topology of the first node;the second obtaining unit is configured to obtain second resourceinformation from a second node according to an isolation policy, wherethe second resource information includes isolation information providedby the second node and a topology of the second node; and the generatingunit is configured to generate a resource topology based on the firstresource information and the second resource information, where theresource topology is used to describe a network topology, an isolationcapability of the first node, an isolation capability of the secondnode, and an isolation capability of a link between the first node andthe second node, and the network topology is a topology between thefirst node and the second node.

In a design of the fourth aspect, the first obtaining unit isspecifically configured to: generate first configuration data accordingto the isolation policy, where the first configuration data is used todescribe the isolation capability of the first node; send the firstconfiguration data to the first node; and receive the first resourceinformation sent by the first node, where the first resource informationincludes the isolation information provided by the first node and thetopology of the first node, and the topology of the first node is usedto describe the first node and a link on which the first node islocated.

In a design of the fourth aspect, the second obtaining unit isspecifically configured to: generate second configuration data accordingto the isolation policy, where the second configuration data is used todescribe the isolation capability of the second node; send the secondconfiguration data to the second node; and receive the second resourceinformation sent by the second node, where the second resourceinformation includes the isolation information provided by the secondnode and the topology of the second node, and the topology of the secondnode is used to describe the second node and a link on which the secondnode is located.

In a design of the fourth aspect, the first obtaining unit isspecifically configured to: obtain the isolation capability of the firstnode according to the isolation policy, where the isolation capabilityof the first node includes isolation capabilities of the first node andthe link on which the first node is located; and generate, based on theisolation capability of the first node and a data model, the firstconfiguration data described by using the data model.

In a design of the fourth aspect, the second obtaining unit isspecifically configured to: obtain the isolation capability of thesecond node according to the isolation policy, where the isolationcapability of the second node includes isolation capabilities of thesecond node and the link on which the second node is located; andgenerate, based on the isolation capability of the second node and thedata model, the second configuration data described by using the datamodel.

In a design of the fourth aspect, the generating unit is specificallyconfigured to: determine a first isolation type based on the isolationinformation provided by the first node and the isolation informationprovided by the second node; and obtain, based on the first isolationtype and the network topology, a first resource topology matching thefirst isolation type, where an isolation capability of a node includedin the first resource topology is the first isolation type, and anisolation capability of a link included in the first resource topologyis the first isolation type.

In a design of the fourth aspect, the generating unit is furtherspecifically configured to: determine a second isolation type based onthe isolation information provided by the first node and the isolationinformation provided by the second node; and obtain, based on the secondisolation type and the network topology, a second resource topologymatching the second isolation type, where an isolation capability of anode included in the second resource topology is the second isolationtype, and an isolation capability of a link included in the secondresource topology is the second isolation type.

In a design of the fourth aspect, the control device further includes athird obtaining unit and an updating unit. The third obtaining unit isconfigured to obtain updated isolation information from the first node,where the updated isolation information is used to describe a newlyadded isolation capability in the first node or an invalid isolationcapability in the first node; and the updating unit is configured toobtain an updated resource topology based on the updated isolationinformation and the resource topology, where the updated resourcetopology is used to describe the network topology, an updated isolationcapability of the first node, the isolation capability of the secondnode, and an updated isolation capability of the link between the firstnode and the second node.

In a design of the fourth aspect, the control device further includes areceiving unit, a fourth obtaining unit, and a creation unit. Thereceiving unit is configured to receive a slice request sent by a user,where the slice request includes an identifier, and the identifier isused to identify an isolation level of a slice requested by the user;the fourth obtaining unit is configured to obtain an isolation type ofthe slice based on the identifier; and the creation unit is configuredto create a network slice based on the isolation type of the slice andthe resource topology, where the resource topology is used to describe anetwork topology and isolation capabilities of N elements in the networktopology, the N elements include at least one of a node and a link, N isan integer greater than or equal to 1, and the network slice includes anode and a link that are required for implementing the slice.

In a design of the fourth aspect, the creation unit may create thenetwork slice according to the method for obtaining a network sliceprovided in one or more designs of the first aspect. The control devicein any one of the fourth aspect or the designs of the fourth aspect isan apparatus configured to obtain a network slice.

According to a fifth aspect, a control device is provided, where thecontrol device includes an orchestrator. The orchestrator is configuredto: receive a slice request sent by a user, where the slice requestincludes an identifier, and the identifier is used to identify anisolation level of a slice requested by the user; obtain an isolationtype of the slice based on the identifier; and create a network slicebased on the isolation type of the slice and a resource topology, wherethe resource topology is used to describe a network topology andisolation capabilities of N elements in the network topology, the Nelements include at least one of a node and a link, N is an integergreater than or equal to 1, and the network slice includes a node and alink that are required for implementing the slice.

In a design of the fifth aspect, the N elements include a first node, asecond node, and a link between the first node and the second node. Theorchestrator is specifically configured to: obtain first resourceinformation from the first node according to an isolation policy, wherethe first resource information includes isolation information providedby the first node and a topology of the first node; obtain secondresource information from the second node according to an isolationpolicy, where the second resource information includes isolationinformation provided by the second node and a topology of the secondnode; and generate a resource topology based on the first resourceinformation and the second resource information, where the resourcetopology is used to describe the network topology, an isolationcapability of the first node, an isolation capability of the secondnode, and an isolation capability of the link between the first node andthe second node, and the network topology is a topology between thefirst node and the second node.

In a design of the fifth aspect, the control device further includes afirst domain controller and a second domain controller. The orchestratoris specifically configured to: generate first configuration dataaccording to the isolation policy, where the first configuration data isused to describe the isolation capability of the first node; andgenerate second configuration data according to the isolation policy,where the second configuration data is used to describe the isolationcapability of the second node. The first domain controller isspecifically configured to: send the first configuration data from theorchestrator to the first node; and receive the first resourceinformation sent by the first node, where the first resource informationincludes the isolation information provided by the first node and thetopology of the first node, and the topology of the first node is usedto describe the first node and a link on which the first node islocated. The second domain controller is specifically configured to:send the second configuration data from the orchestrator to the secondnode; and receive the second resource information sent by the secondnode, where the second resource information includes the isolationinformation provided by the second node and the topology of the secondnode, and the topology of the second node is used to describe the secondnode and a link on which the second node is located.

In one or more designs of the fifth aspect, the orchestrator canimplement any design of the first aspect. The control device in any oneof the fifth aspect or the designs of the fifth aspect is an apparatusconfigured to obtain a network slice.

According to a sixth aspect, a control device is provided, where thecontrol device includes an orchestrator. The orchestrator isspecifically configured to: obtain first resource information from afirst node according to an isolation policy, where the first resourceinformation includes isolation information provided by the first nodeand a topology of the first node; obtain second resource informationfrom a second node according to an isolation policy, where the secondresource information includes isolation information provided by thesecond node and a topology of the second node; and generate a resourcetopology based on the first resource information and the second resourceinformation, where the resource topology is used to describe a networktopology, an isolation capability of the first node, an isolationcapability of the second node, and an isolation capability of a linkbetween the first node and the second node, and the network topology isa topology between the first node and the second node.

In a design of the sixth aspect, the control device further includes afirst domain controller. The orchestrator is specifically configured to:generate first configuration data according to the isolation policy,where the first configuration data is used to describe the isolationcapability of the first node; send the first configuration data to thefirst node by using the first domain controller; and receive, by usingthe first domain controller, the first resource information sent by thefirst node, where the first resource information includes the isolationinformation provided by the first node and the topology of the firstnode, and the topology of the first node is used to describe the firstnode and a link on which the first node is located.

In a design of the sixth aspect, the control device further includes asecond domain controller. The orchestrator is specifically configuredto: generate second configuration data according to the isolationpolicy, where the second configuration data is used to describe theisolation capability of the second node; send the second configurationdata to the second node by using the second domain controller; andreceive, by using the second domain controller, the second resourceinformation sent by the second node, where the second resourceinformation includes the isolation information provided by the secondnode and the topology of the second node, and the topology of the secondnode is used to describe the second node and a link on which the secondnode is located.

In a design of the sixth aspect, the orchestrator is specificallyconfigured to: obtain the isolation capability of the first nodeaccording to the isolation policy, where the isolation capability of thefirst node includes isolation capabilities of the first node and thelink on which the first node is located; and generate, based on theisolation capability of the first node and a data model, the firstconfiguration data described by using the data model.

In a design of the sixth aspect, the orchestrator is specificallyconfigured to: obtain the isolation capability of the second nodeaccording to the isolation policy, where the isolation capability of thesecond node includes isolation capabilities of the second node and thelink on which the second node is located; and generate, based on theisolation capability of the second node and the data model, the secondconfiguration data described by using the data model.

In a design of the sixth aspect, the orchestrator is specificallyconfigured to: determine a first isolation type based on the isolationinformation provided by the first node and the isolation informationprovided by the second node; and obtain, based on the first isolationtype and the network topology, a first resource topology matching thefirst isolation type, where an isolation capability of a node includedin the first resource topology is the first isolation type, and anisolation capability of a link included in the first resource topologyis the first isolation type.

In a design of the sixth aspect, the orchestrator is furtherspecifically configured to: determine a second isolation type based onthe isolation information provided by the first node and the isolationinformation provided by the second node; and obtain, based on the secondisolation type and the network topology, a second resource topologymatching the second isolation type, where an isolation capability of anode included in the second resource topology is the second isolationtype, and an isolation capability of a link included in the secondresource topology is the second isolation type.

In a design of the sixth aspect, the orchestrator is specificallyconfigured to: obtain updated isolation information from the first node,where the updated isolation information is used to describe a newlyadded isolation capability in the first node or an invalid isolationcapability in the first node; and obtain an updated resource topologybased on the updated isolation information and the resource topology,where the updated resource topology is used to describe the networktopology, an updated isolation capability of the first node, theisolation capability of the second node, and an updated isolationcapability of the link between the first node and the second node. Theorchestrator may obtain updated isolation information from the firstnode by using the first domain controller.

In a design of the sixth aspect, the orchestrator is specificallyconfigured to: receive a slice request sent by a user, where the slicerequest includes an identifier, and the identifier is used to identifyan isolation level of a slice requested by the user; obtain an isolationtype of the slice based on the identifier; and create a network slicebased on the isolation type of the slice and the resource topology,where the resource topology is used to describe the network topology andisolation capabilities of N elements in the network topology, the Nelements include at least one of a node and a link, N is an integergreater than or equal to 1, and the network slice includes a node and alink that are required for implementing the slice.

In a design of the sixth aspect, the orchestrator may create the networkslice according to the method for creating a network slice provided inone or more designs of the first aspect.

According to a seventh aspect, a computer-readable storage medium isprovided. The computer-readable storage medium includes an instruction,and when the instruction is run on a computer, the computer is enabledto perform the method for obtaining a network slice according to any oneof the first aspect or the possible designs of the first aspect.

According to an eighth aspect, a computer-readable storage medium isprovided. The computer-readable storage medium includes an instruction,and when the instruction is run on a computer, the computer is enabledto perform the method for obtaining a resource topology according to anyone of the second aspect or the possible designs of the second aspect.

According to a ninth aspect, a computer program product including aninstruction is provided. When the computer program product is run on acomputer, the computer is enabled to perform the method for obtaining anetwork slice according to any one of the first aspect or the possibledesigns of the first aspect.

According to a tenth aspect, a computer program product including aninstruction is provided. When the computer program product is run on acomputer, the computer is enabled to perform the method for obtaining aresource topology according to any one of the second aspect or thepossible designs of the second aspect.

According to an eleventh aspect, a control device is provided. Thecontrol device includes a processor, a memory, a bus, and acommunications interface. The memory is configured to store acomputer-executable instruction. The processor and the memory areconnected by using the bus. When the control device operates, theprocessor executes the computer-executable instruction stored in thememory, to enable the control device to perform the method for obtaininga network slice according to any one of the first aspect or the possibledesigns of the first aspect. The control device may be the controldevice mentioned in any one of the first aspect or the possible designsof the first aspect.

According to a twelfth aspect, a control device is provided. The controldevice includes a processor, a memory, a bus, and a communicationsinterface. The memory is configured to store a computer-executableinstruction. The processor and the memory are connected by using thebus. When the control device operates, the processor executes thecomputer-executable instruction stored in the memory, to enable thecontrol device to perform the method for obtaining a resource topologyaccording to any one of the second aspect or the possible designs of thesecond aspect. The control device may be the control device mentioned inany one of the second aspect or the possible designs of the secondaspect.

According to a thirteenth aspect, a network device is provided. Thenetwork device includes a receiving unit, an obtaining unit, and asending unit. The receiving unit is configured to receive configurationdata from a control device, where the configuration data is used todescribe an isolation capability of the network device. The obtainingunit is configured to obtain sub-resource information based on theconfiguration data, where the sub-resource information includesisolation information provided by the network device and a topology ofthe network device, and the topology of the network device is used todescribe the network device and a link on which the network device islocated. The sending unit is configured to send the sub-resourceinformation to the control device.

According to a fourteenth aspect, a network device is provided. Thenetwork device includes a processor, a memory, a bus, and acommunications interface. The memory is configured to store acomputer-executable instruction. The processor and the memory areconnected by using the bus. When the control device operates, theprocessor executes the computer-executable instruction stored in thememory, to enable the network device to perform the followingoperations: receiving configuration data from a control device, wherethe configuration data is used to describe an isolation capability ofthe network device; obtaining sub-resource information based on theconfiguration data, where the sub-resource information includesisolation information provided by the network device and a topology ofthe network device, and the topology of the network device is used todescribe the network device and a link on which the network device islocated; and sending the sub-resource information to the control device.

The network device provided in the thirteenth aspect or the fourteenthaspect may be the first node in any one of the first aspect or thedesigns of the first aspect, or the second node in any one of the secondaspect or the designs of the second aspect.

According to a fifteenth aspect, a system for obtaining a network sliceis provided. The system includes the network device provided in thetwelfth aspect or the thirteenth aspect, and the control device providedin any one of the third aspect to the eleventh aspect or any design ofany one of the third aspect to the eleventh aspect.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of thisapplication more clearly, the following briefly describes theaccompanying drawings required for describing the embodiments.

FIG. 1 is a schematic diagram of a network scenario of obtaining anetwork slice;

FIG. 2 is a schematic diagram of a network scenario according toEmbodiment 1 of this application;

FIG. 3 is a schematic flowchart of a method for obtaining a networkslice according to Embodiment 1 of this application;

FIG. 4A and FIG. 4B are schematic diagrams of performing isolation levelclassification on a network resource according to Embodiment 1 of thisapplication;

FIG. 5 is a schematic diagram of a network scenario according toEmbodiment 2 of this application;

FIG. 6 is a schematic structural diagram of a control device accordingto Embodiment 3 of this application;

FIG. 7 is a schematic structural diagram of a control device accordingto Embodiment 4 of this application;

FIG. 8 is a schematic structural diagram of a control device accordingto Embodiment 5 of this application;

FIG. 9 is a schematic structural diagram of a control device accordingto Embodiment 6 of this application; and

FIG. 10 is a schematic structural diagram of a system used to obtain anetwork slice according to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

The following describes the embodiments of the present invention withreference to accompanying drawings.

Embodiment 1

FIG. 2 is a schematic diagram of a network scenario according toEmbodiment 1 of this application. In the scenario shown in FIG. 2 , adomain A includes a plurality of nodes, for example, R1 and R3 in FIG. 2. R1 and R3 may be edge nodes in the domain A. A domain B includes atleast one node, for example, R2 in FIG. 2 . R2 may be an edge node inthe domain B. The domain A may be a wireless network, a bearer network,or a core network. The domain B may be a wireless network, a bearernetwork, or a core network. The domain A and the domain B may be subnetsin a same network, or the domain A and the domain B may be differentnetworks. A control device can communicate with nodes in the domain Aand the domain B, and configure the nodes in the domain A and the domainB. R1 and R2 may communicate with each other through a plurality ofpaths, for example, P1 and P2 in FIG. 2 . P1 and P2 are used to identifydifferent paths. A path identified by P1 may be represented as R1-R2. Apath identified by P2 may be represented as R1-R3-R2. The node in thisembodiment of this application may be a forwarding device or a server inthe network. The forwarding device in the network may be a router or aswitch. The control device in this embodiment may be a software-definednetworking (SDN) controller or a controller of another type.

FIG. 3 is a schematic flowchart of a method for obtaining a networkslice according to Embodiment 1 of this application. The method providedin Embodiment 1 of this application is described below with reference toFIG. 2 and FIG. 3 .

301: A control device generates first configuration data and secondconfiguration data according to an isolation policy.

For example, the first configuration data is used to describe anisolation capability of a first node, and the second configuration datais used to describe an isolation capability of a second node. Thecontrol device may receive an isolation policy delivered by an operationsupport system (OSS). The isolation policy is used to describe isolationlevels of a node in a network and a link on which the node is located.The isolation policy may be set based on isolation levels shown in FIG.4A and FIG. 4B. Specifically, the control device obtains, according tothe isolation policy, the isolation capability of the first node and theisolation capability of the second node. The isolation capability of thefirst node includes isolation capabilities of the first node and linkson which the first node is located. The isolation capability of thesecond node includes isolation capabilities of the second node and linkson which the second node is located. The isolation capability mentionedin this embodiment of this application is an isolation function (anisolation level or an isolation function included in the isolation levelshown in FIG. 4A and FIG. 4B) that can be implemented by an element inthe network, and the element in the network is a node in the network ora link in the network.

The control device generates the first configuration data based on theisolation capability of the first node and a data model. The controldevice generates the second configuration data based on the isolationcapability of the second node and the data model. The data model used bythe control device may be a YANG model. The links on which the firstnode is located include a link on which the first node is a start node,a link on which the first node is an intermediate node, and a link onwhich the first node is an end node. The links on which the second nodeis located include a link on which the second node is a start node, alink on which the second node is an intermediate node, and a link onwhich the second node is an end node.

When isolation level classification is performed based on an isolationgranularity, resources in the network may be classified into three types(as shown in a cylindrical classification diagram in FIG. 4A and FIG.4B): (1) resources having a fine-grained physical isolation capability;(2) resources having a coarse-grained physical isolation capability; and(3) resources that do not have a physical isolation capability (whichare resources having a logical isolation capability). A condition forperforming coarse-grained physical isolation by using the resources oftype (2) is that a physical device or a physical port is not used by aslice. If the physical device or the physical port is used by a slice,the resources of type (2) can no longer implement the isolationfunction. The resources of type (3) are resources that do not have aphysical isolation capability, but a resource of type (3) may be used bya plurality of network slices that have a sharing feature. For example,if a rate of a physical link is 100 G, and a 50 G bandwidth has beenoccupied by a network slice, the remaining 50 G bandwidth of the link isa resource of type (3). Resource topologies of four types may beobtained based on the foregoing resources of the three types: a resourcetopology that corresponds to the resources of type (1) and that has afine-grained physical isolation capability, a resource topology thatcorresponds to the resources of type (1) and type (2) and that has aphysical isolation capability, a resource topology that corresponds tothe resources of type (3) and that has a logical isolation capability,and an all-resource topology corresponding to the resources of the threetypes. The resources of type (1) and type (2) may further provide alogical isolation capability. When the resource topology having thelogical isolation capability is obtained by using the resource of type(3), the resource topology having the logical isolation capability maybe further obtained based on the resources of type (2) and type (3), orthe resource topology having the logical isolation capability isobtained based on the resources of type (1) and type (3). As shown inFIG. 4A and FIG. 4B, isolation levels of the foregoing three types ofresources may be further classified. Isolation levels of resourceshaving the physical isolation capability may be further classified intoa slot level, a wavelength level, a port level, a device level, and anetwork level. For the slot level, isolation capability classificationis performed based on the flexible ethernet (FlexE), an optical channeldata unit (ODUk), or a transmission container (T-cont). For thewavelength level, isolation capability classification is performed basedon a ratio of a wavelength to a frequency. For the port level, isolationcapability classification is performed based on a physical port,flexible ethernet (FlexE) cross, an optical cross-connection, or anetwork processor (NP)+traffic management (TM). An isolation capabilitysupporting the FlexE cross indicates that the FlexE cross is supportedin the ethernet. An isolation capability supporting the opticalcross-connection indicates that the optical cross-connection issupported in an optical network. An isolation capability supportingNP+TM indicates that both NP isolation and TM isolation are supported.For the device level, isolation capability classification is performedbased on a device attribute. For the network level, isolation capabilityclassification is performed based on a network attribute. The networkattribute can be a home-customer-dedicated network, agroup-customer-dedicated network, a 5G-bearer-dedicated network, or ashared network. The shared network may be applicable to all services.Isolation levels of the resources having the logical isolationcapability may be further performed according to a user level, a servicelevel, a tunnel level, and a system level. For the service level,isolation capability classification is performed based on a virtualprivate network (VPN). For the tunnel level, isolation capabilityclassification is performed based on a tunnel attribute. For anisolation capability of the system level, isolation capabilityclassification may be performed based on a virtual system (VS), forexample, isolation capability classification based on a virtual port(VI) of the virtual system. If identification is performed based on anisolation granularity, resources of the user level and the service levelare fine-grained logical isolation resources; resources of the tunnellevel and the system level are coarse-grained logical isolationresources; resources of the slot level, the wavelength level, forwardingisolation, and cross-connection isolation are fine-grained physicalisolation resources; and resources of the port level, the device level,the network level, and system isolation are coarse-grained physicalisolation resources. For the forwarding isolation, the cross-connectionisolation, and the system isolation, isolation level classification isfurther performed based on isolation of the device level.

When isolation capability classification is performed based on anisolation technology, resources in the network may be classified intothree types: (1) resources having a network isolation capability; (2)resources having a node isolation capability; and (3) resources having alink isolation capability. Isolation levels of the resources having thenetwork isolation capability may be further classified into a (1.1)home-customer-dedicated network, a (1.2) group-customer-dedicatednetwork, a (1.3) 5G-bearer-dedicated network, and a (1.4) sharednetwork. Isolation levels of the resources having the node isolationcapability may be further classified into an (2.1) all-port level, a(2.2) part-of-port level, a (2.3) system level, and a (2.4) logic level.For the (2.1) all-port level, isolation capability classification may beperformed based on NP+TM. For the (2.2) part-of-port level, isolationcapability classification may be performed based on a FlexE cross or anoptical cross-connection. For the (2.3) system level, isolationcapability classification is performed based on a VI. A resource of the(2.4) logical level is a node that has a logical isolation capabilitybut does not have a physical isolation capability. Isolation levels ofthe resources having the link isolation capability may be furtherclassified into a (3.1) slot level, a (3.2) wavelength level, a (3.3)physical-port level, and a (3.4) logic level. For the (3.1) slot level,isolation capability classification is performed based on FlexE, ODUk,or T-cont. For the (3.2) wavelength level, isolation capabilityclassification is performed based on a ratio of a wavelength to afrequency. For the (3.3) physical-port level, isolation capabilityclassification is performed based on a physical port included on a link.A resource of the (3.4) logical level is a link that has a logicalisolation capability but does not have a physical isolation capability.

For example, the control device may obtain a correspondence according tothe isolation policy, where the isolation policy includes an isolationlevel used for an element in a network of a specific type. The networkof the specific type may be selected from (1.1) to (1.4). The element inthe network may be a node, a link, or a node TP. The isolation level maybe selected from the isolation levels in FIG. 4A and FIG. 4B. Thecorrespondence includes a network identifier and a resourceclassification table. The resource classification table includes theelement in the network and the isolation level of the element. In thescenario shown in FIG. 2 , the isolation policy obtained by the controldevice is to use the following isolation levels for anon-home-customer-dedicated network:

(1) A node having an NP+TM isolation capability satisfies the nodeisolation level corresponding to (2.1). Using four bits to represent anisolation capability of the node, where the four bits respectivelyrepresent, from left to right, the isolation levels corresponding to(2.1), (2.2), (2.3), and (2.4), an isolation level of the node isrepresented as “1000”. The isolation level of the node identified by“1000” indicates that the node has the all-port level isolationcapability.

(2) A link having a FlexE isolation capability satisfies the linkisolation level corresponding to (3.1). Using four bits to represent anisolation capability of the link, where the four bits respectivelyrepresent, from left to right, the isolation levels corresponding to(3.1), (3.2), (3.3), and (3.4), an isolation level of the link isrepresented as “1000”. The isolation level of the link identified by“1000” indicates that the link has the slot-level isolation capability.

(3) A link having a physical-port isolation capability satisfies thelink isolation level corresponding to (3.3). Using four bits torepresent an isolation capability of the link, where the four bitsrespectively represent, from left to right, the isolation levelscorresponding to (3.1), (3.2), (3.3), and (3.4), an isolation level ofthe link is represented as “0010”. The isolation level of the linkidentified by “0010” indicates that the link has the physical-port-levelisolation capability.

The control device may configure data for R1, R2, and R3 based on theforegoing isolation policy. Configuration data of R1, R2, and R3 may bedescribed by using the following YANG data model. Details are asfollows:

  augment ../../../nw:node/node-id   grouping node-attributes {     case ″node-isolated-attributes = ′NP+TMenable ′ ″ ;      leafnode-isolated-level{ type uint16 { value ″1000″; } } //node isolation is1000     }    grouping link-attributes {      case″source-tp=flexeenabled & dest-tp=flexeenable”;      leaflink-isolated-level{ type uint16 { value ″1000″; } } //link isolation is1000     }   grouping link-attributes {      case ″source-tp=physical-port & dest-tp=physical-port”;      leaf link-isolated-level{type uint16 { value ″0010″; } } //link isolation is 0010     }

302: The control device sends the first configuration data to the firstnode, and then the first node performs 304.

303: The control device sends the second configuration data to thesecond node, and then the second node performs 306.

In 302 and 303, by using the network configuration protocol (NETCONF),the control device may send, to the first node, the first configurationdata described by using the YANG data model, and send, to the secondnode, the second configuration data described by using the YANG datamodel. In the scenario shown in FIG. 2 , the control device respectivelysends, to R1, R2, and R3 by using NETCONF, the configuration datadescribed in the YANG data model in 301.

304: The first node obtains first resource information based on thefirst configuration data.

For example, an attribute of each TP of the first node is configured onthe first node. The attribute of the TP is used to indicate an isolationcapability supported by the TP. The first node obtains, based on thefirst configuration data from the control device, identifiers of M1 TPsthat meet an isolation capability in the first configuration data and anidentifier of the first node. The M1 TPs include at least one ingress TPand at least one egress TP. The first node obtains the first resourceinformation based on the identifiers of the M1 TPs, isolationcapabilities of the M1 TPs, and the identifier of the first node. Thefirst resource information includes isolation information provided bythe first node and a topology of the first node. The isolationinformation provided by the first node is used to indicate an isolationcapability that the first node has and that matches the firstconfiguration data, for example, an isolation capability corresponds toa TP that is on the first node and that matches the first configurationdata. For details, refer to a part of the first node in resourceinformation described by using the YANG model in 308. The topology ofthe first node is a physical topology of the first node, or the topologyof the first node is a logical topology of the first node. The topologyof the first node is used to describe the first node and the links onwhich the first node is located. The links on which the first node islocated may be represented by TPs connecting the first node to eachlink. The TP connecting the first node to a link may be referred to as alink terminal point (TP) of the first node. A link in this embodiment ofthis application is a physical link, or a link is a logical link.

305: The first node sends the first resource information to the controldevice, and then the control device performs 308.

For example, the first node may send the first resource information tothe control device by using NETCONF. The first resource information maybe described by using the YANG model.

306: The second node obtains second resource information based on thesecond configuration data.

For example, an attribute of each TP of the second node is configured onthe second node. The attribute of the TP is used to indicate anisolation capability supported by the TP. The second node obtains, basedon the second configuration data from the control device, identifiers ofM2 TPs that meet an isolation capability in the second configurationdata and an identifier of the second node. The M2 TPs include at leastone ingress TP and at least one egress TP. The second node obtains thesecond resource information based on the identifiers of the M2 TPs,isolation capabilities of the M2 TPs, and the identifier of the secondnode. The second resource information includes isolation informationprovided by the second node and a topology of the second node. Theisolation information provided by the second node is used to indicate anisolation capability that the second node has and that matches thesecond configuration data, for example, an isolation capabilitycorresponding to a TP that is on the second node and that matches thesecond configuration data. For details, refer to a part of the secondnode in resource information described by using the YANG model in 308.The topology of the second node is a physical topology of the secondnode, or the topology of the second node is a logical topology of thesecond node. The topology of the second node is used to describe thesecond node and the links on which the second node is located. The linkson which the second node is located may be represented by TPs connectingthe second node to a link. The TP connecting the second node to the linkmay be referred to as a link terminal point (TP) of the second node. Alink in this embodiment of this application is a physical link, or alink is a logical link.

307: The second node sends the second resource information of the secondnode to the control device, and then the control device performs 308.

For example, the second node may send the second resource information tothe control device by using NETCONF. The second resource information maybe described by using the YANG model.

308: The control device generates a resource topology.

For example, the control device obtains resource information based onthe first resource information from the first node and the secondresource information from the second node. The resource informationincludes the topology of the first node, the topology of the secondnode, the isolation information provided by the first node, and theisolation information provided by the second node. A set formed by thetopology of the first node and the topology of the second node is usedto describe a topology between the first node and the second node, forexample, a node and a link that can perform communication between thefirst node and the second node, or a link that can perform communicationbetween the first node and the second node. In the scenario shown inFIG. 2 , R1 and R2 may communicate with each other by using the twolinks P1 and P2. If R1 is the first node, and R2 is the second node, atopology between R1 and R2 includes R1, R2, R3, P1, and P2. R1, R2, andR3 all have the (2.1) all-port level isolation capability. R1, R2, andR3 respectively have three, three, and two link TPs. Identifiers of thethree link TPs of R1 are respectively 1-0-1, 1-2-1, and 1-3-1. The linkTP identified by 1-2-1 can communicate with R2. The link TP identifiedby 1-3-1 can communicate with R3. Identifiers of the two link TPs of R3are respectively 3-1-1 and 3-2-1. The link TP identified by 3-1-1 cancommunicate with R1. The link TP identified by 3-2-1 can communicatewith R2. Identifiers of the three link TPs of R2 are respectively 2-1-1,2-0-1, and 2-3-1. The link TP identified by 2-1-1 can communicate withR1. The link TP identified by 2-3-1 can communicate with R3. P1 has the(3.3) physical-port-level isolation capability. Bandwidth link_rate ofP1 is 50 G. P2 has the (3.1) slot-level isolation capability. Bandwidthlink_rate of P2 is 30 G. The control device may obtain resourceinformation corresponding to the domain A and the domain B based onresource information from R1, resource information from R2, and resourceinformation from R3. The resource information corresponding to thedomain A and the domain B may be represented, by using the YANG model,as follows:

 {   ″ietf-network:networks″: {    ″network″: [     {     ″network-types″: {      },      ″network-id″: ″otn-hc″,     ″network-attributes″: ″0111″,  //An isolation level (a networktype) corresponding to a network isolation capability      ″node″: [      {        ″node-id″: ″R1″,        ″node-isolated-level″: ″1000″, //An isolation level corresponding to a node isolation capability       ″node-isolated-tp″: ″all″,        ″termination-point″: [        {          ″tp-id″: ″1-0-1″         },         {         ″tp-id″: ″1-2-1″         },         {          ″tp-id″: ″1-3-1″        }        ]       },       {        ″node-id″: ″R2″,       ″node-isolated-level″: ″1000″,  //An isolation levelcorresponding to a node isolation capability        ″node-isolated-tp″:″all″,        ″termination-point″: [         {          ″tp-id″: ″2-0-1″        },         {          ″tp-id″: ″2-1-1″         },         {         ″tp-id″: ″2-3-1″         }        ]       },       {       ″node-id″: ″R3″,        ″node-isolated-level″: ″1000″,  //Anisolation level corresponding to a node isolation capability       ″node-isolated-tp″: all″,        ″termination-point″: [         {         ″tp-id″: ″3-1-1″         },         {          ″tp-id″: ″3-2-1″        }        ]       }      ],      ″ietf-network-topology:link″: [      {        ″link-id″: ″R1,1-2-1,R2,2-1-1″,       ″link-isolated-level″: ″0010″,  //An isolation levelcorresponding to a link isolation capability        ″link-rate″: ″50G″,       ″destination″: {         ″source-node″: ″R1″,        ″source-tp″: ″1-2-1″        }        ″destination″: {        ″dest-node″: ″R2″,         ″dest-tp″: ″2-1-1″        }       },      {        ″link-id″: ″R2,2-1-1,R1,1-2-1″,       ″link-isolated-level″: ″0010″,  //An isolation levelcorresponding to a link isolation capability        ″link-rate″: ″50G″,       ″destination″: {         ″source-node″: ″R2″,        ″source-tp″: ″2-1-1″        }        ″destination″: {        ″dest-node″: ″R1″,         ″dest-tp″: ″1-2-1″        }       },      {        ″link-id″: ″R1,1-3-1,R3,3-1-1″,       ″link-isolated-level″: ″1000″,  //An isolation levelcorresponding to a link isolation capability        ″link-rate″: ″30G″,       ″destination″: {         ″source-node″: ″R1″,        ″source-tp″: ″1-3-1″        }        ″destination″: {        ″dest-node″: ″R3″,         ″dest-tp″: ″3-1-1″        }       },      {        ″link-id″: ″R3,3-1-1,R1,1-3-1″,       ″link-isolated-level″: ″1000″,  //An isolation levelcorresponding to a link isolation capability        ″link-rate″: ″30G″,       ″destination″: {         ″source-node″: ″R3″,        ″source-tp″: ″3-1-1″        }        ″destination″: {        ″dest-node″: ″R1″,         ″dest-tp″: ″1-3-1″        }       },      {        ″link-id″: ″R2,2-3-1,R3,3-2-1″,       ″link-isolated-level″: ″1000″,  //An isolation levelcorresponding to a link isolation capability        ″link-rate″: ″30G″,       ″destination″: {         ″source-node″: ″R2″,        ″source-tp″: ″2-3-1″        }        ″destination″: {        ″dest-node″: ″R3″,         ″dest-tp″: ″3-2-1″        }       },      {        ″link-id″: ″R3,3-2-1,R2,2-3-1″,       ″link-isolated-level″: ″1000″,  //An isolation levelcorresponding to a link isolation capability        ″link-rate″: ″30G″,       ″destination″: {         ″source-node″: ″R3″,        ″source-tp″: ″3-2-1″        }        ″destination″: {        ″dest-node″: ″R2″,         ″dest-tp″: ″2-3-1″        }       }     ]     }    ]   }  }

For example, that the control device generates the resource topologybased on the resource information includes: determining, by the controldevice, a first isolation type based on the isolation informationprovided by the first node and the isolation information provided by thesecond node; and obtaining, by the control device based on the firstisolation type and a topology, a first resource topology matching thefirst isolation type, where an isolation capability of a node includedin the first resource topology is the first isolation type, and anisolation capability of a link included in the first resource topologyis the first isolation type. When the resource topology includessub-resource topologies of a plurality of isolation types, for example,the resource topology includes the first resource topology and a secondresource topology, in addition to the first resource topology obtainedby the control device by using the foregoing method, the control devicemay further obtain the second resource topology. A method for obtainingthe second resource topology by the control device includes:determining, by the control device, a second isolation type based on theisolation information provided by the first node and the isolationinformation provided by the second node; and obtaining, by the controldevice based on the second isolation type and the topology, the secondresource topology matching the second isolation type, where an isolationcapability of a node included in the second resource topology is thesecond isolation type, and an isolation capability of a link included inthe second resource topology is the second isolation type. The topologyis a physical topology or a logical topology obtained by the controldevice based on the topology of the first node and the topology of thesecond node. The first isolation type and the second isolation type maybe types used to indicate isolation granularities, for example,fine-grained physical isolation, coarse-grained physical isolation, orlogical isolation. In the scenario shown in FIG. 2 , based on theresources obtained through division based on the isolation granularitiesin 301, the control device may form four types of resource topologies,that is, a resource topology having a fine-grained physical isolationcapability, a resource topology having a coarse-grained physicalisolation capability, a resource topology having a logical isolationcapability, and an all-resource topology. P1 has a coarse-grainedphysical isolation capability, and therefore R1-R2 forms a resourcetopology having the coarse-grained physical isolation capability.Although R1 and R2 have a fine-grained physical isolation capability,the fine-grained physical isolation capability of R1 and R2 may bedownward compatible with the coarse-grained physical isolationcapability, that is, the isolation capability of the resource topologyformed between R1 and R2 is determined by a low-level isolationcapability. P2 has a fine-grained physical isolation capability, andtherefore R1-R3-R2 forms a resource topology having the fine-grainedphysical isolation capability.

309: The control device receives a slice request sent by a user.

For example, the slice request sent by the user includes an identifier,and the identifier is used to describe an isolation level of a slicerequested by the slice request. The identifier may be information or aparameter directly identifying the isolation level. Alternatively, theidentifier may be information or a parameter used to identify a servicetype. The service type corresponds to the isolation level. The controldevice may determine an isolation type based on the information or theparameter used to identify the service type. The control device performslookup in the correspondence based on the isolation level, to obtain anisolation type that matches the isolation level. Isolation types andisolation levels may be classified based on different dimensions. In animplementation, the isolation type may be fine-grained physicalisolation, coarse-grained physical isolation, or logical isolation. Inanother implementation, the isolation type may be network isolation,node isolation, or link isolation. Isolation levels of the isolationtypes may be further classified. An isolation level is used to describean isolation requirement. In an implementation, the isolation level maybe highest-level isolation, lowest-level isolation, common-levelisolation, or no isolation. The control device may determine, based onthe isolation level, an isolation type that matches the isolation level.For example, an isolation type matching the highest-level isolation isfine-grained physical isolation, an isolation type matching thecommon-level isolation is fine-grained physical isolation, an isolationtype matching the lowest-level isolation is coarse-grained physicalisolation, and an isolation type matching the no isolation is logicalisolation. In another implementation, the isolation level may be a userlevel, a service level, a tunnel level, a system level, a slot level, awavelength level, a port level, a device level, or a network level. Thecontrol device may determine, based on the isolation level, an isolationtype that matches the isolation level. For example, an isolation typematching the service-level isolation is logical isolation or linkisolation, and an isolation type matching the NP+TM (port-level)isolation is coarse-grained physical isolation or node isolation. Fordetails, refer to content of FIG. 4A and FIG. 4B and relateddescriptions. In the scenario shown in FIG. 2 , according to a firstslice request sent by the user, a first network slice needs to bedeployed. A bandwidth required for the first network slice is 40 G. Anidentifier included in the first slice request is used to indicate thatan isolation level of the first network slice is the lowest-levelisolation. According to a second slice request sent by the user, asecond network slice needs to be deployed. A bandwidth required for thesecond network slice is 10 G. An identifier included in the second slicerequest is used to indicate that an isolation level of the secondnetwork slice is the highest-level isolation. According to a third slicerequest sent by the user, a third network slice needs to be deployed. Abandwidth required for the third network slice is 10 G. An identifierincluded in the third slice request is used to indicate that anisolation level of the third network slice is the highest-levelisolation.

310: The control device selects, from the resource topology based on theslice request, a network resource that meets the slice request.

For example, when the isolation type is fine-grained physical isolation,the control device calculates, in a resource topology having thefine-grained physical isolation capability, the network resourcerequired by the slice request. If the resource topology having thefine-grained physical isolation capability cannot meet the networkresource required by the slice request, the control device outputs analarm signal for prompting. When the isolation type is coarse-grainedphysical isolation, the control device calculates, in a resourcetopology having the coarse-grained physical isolation capability, thenetwork resource required by the slice request. If the resource topologyhaving the coarse-grained physical isolation capability can meet thenetwork resource required by the slice request, the control deviceselects a network resource from the resource topology having thecoarse-grained physical isolation capability. If the resource topologyhaving the coarse-grained physical isolation capability cannot meet thenetwork resource required by the slice request, the control devicecalculates, in the resource topology having the fine-grained physicalisolation capability, the network resource required by the slicerequest. If a topology formed by a resource having the fine-grainedphysical isolation capability and a resource having the coarse-grainedphysical isolation capability can meet the network resource required bythe slice request, the control device selects a network resource fromthe resource topology having the coarse-grained physical isolationcapability and the fine-grained physical isolation capability. If thetopology formed by the resource having the fine-grained physicalisolation capability and the resource having the coarse-grained physicalisolation capability cannot meet the network resource required by theslice request, the control device outputs an alarm signal for prompting.If the control device determines, based on the identifier included inthe slice request, that isolation is not required, the control devicecalculates, in a resource topology having the logical isolationcapability, the network resource required by the slice request.

In the scenario shown in FIG. 2 , the bandwidth required for the firstnetwork slice is 40 G. The control device determines, based on anidentifier included in the first slice request, that the first networkslice corresponds to coarse-grained physical isolation. The controldevice determines, based on the resource topology in 308, that thecoarse-grained physical resource topology between R1 and R2 can meet arequirement of the first network slice. The bandwidth required for thesecond network slice is 10 G. The control device determines, based on anidentifier included in the second slice request, that the second networkslice corresponds to fine-grained physical isolation. The control devicedetermines, based on the resource topology in 308, that the fine-grainedphysical resource topology between R1, R3, and R2 can meet a requirementof the second network slice. The bandwidth required for the thirdnetwork slice is 10 G. The control device determines, based on anidentifier included in the third slice request, that the third networkslice corresponds to fine-grained physical isolation. The control devicedetermines, based on the resource topology in 308, that the fine-grainedphysical resource topology between R1, R3, and R2 can meet a requirementof the third network slice.

311: The control device creates a network slice.

For example, after calculating the network resource required by theslice request, the control device stores a correspondence between thenetwork resource and the network slice. The control device generates Nto-be-configured nodes and configuration information of the N nodesbased on the network resource, where N is an integer greater than 1. TheN to-be-configured nodes are nodes in the network resource. A topologyformed by the N to-be-configured nodes is used to implement a servicecorresponding to the slice request. The control device delivers thegenerated configuration information to corresponding nodes, therebycreating the network slice. In the scenario shown in FIG. 2 , thecontrol device selects, based on the bandwidth of P1 and the first slicerequest, P1 for deployment of the first network slice. The controldevice delivers configuration information corresponding to the firstnetwork slice to TPs that are related to P1 and that are on R1 or R2.The control device selects, based on the bandwidth of P2 and the secondslice request, P2 for deployment of the second network slice. Thecontrol device delivers configuration information corresponding to thesecond network slice to TPs that are related to P2 and that are on R1,R3, or R2. The control device selects, based on the bandwidth of P2 andthe third slice request, P2 for deployment of the third network slice.The control device delivers configuration information corresponding tothe third network slice to TPs that are related to P2 and that are onR1, R3, or R2. The control device further stores a correspondencebetween the first network slice and a network resource that is on P1 andthat meets the requirement of the first network slice, a correspondencebetween the second network slice and a network resource that is on P2and that meets the requirement of the second network slice, and acorrespondence between the third network slice and a network resourcethat is on P2 and that meets the requirement of the third network slice.

After the control device creates the network slice, the isolationcapability of the first node or the second node is changed. A node whoseisolation capability is changed may communicate with the control device,so that the control device updates the generated resource topology. Amethod for updating the resource topology by the control device isdescribed below by using an example in which the isolation capability ofthe first node is changed. After 311, the method provided in thisembodiment of this application further includes: obtaining, by thecontrol device, updated isolation information from the first node, wherethe updated isolation information is used to describe a newly addedisolation capability in the first node or an invalid isolationcapability in the first node; and updating, by the control device, theresource topology in 308 based on the updated isolation information andthe resource topology generated in 308, thereby obtaining an updatedresource topology. The updated resource topology is used to describe thetopology, an updated isolation capability of the first node, theisolation capability of the second node, and an updated isolationcapability of the link between the first node and the second node. Afterthe isolation capability of the first node is changed, a parameter thatis in the resource topology generated in 308 and related to theisolation capability of the first node needs to be updated, but thetopology between the first node and the second node is not changed. Whenboth the topology of the first node and the isolation capability of thefirst node are changed, the control device further needs to update thetopology in the resource topology generated in 308.

In the method provided in this embodiment of this application, thecontrol device can determine the isolation type of the slice based onthe slice request, and thereby select, from the resource topology basedon the isolation type, an element for implementing the slice, so that anisolation capability of the selected element matches the isolation type.Further, the control device generates, based on an isolation capabilityof an element in the network, a resource topology that can support someisolation capabilities. In this way, when creating the network slice,the control device may generate, based on the isolation capabilitysupported by the resource topology, a slice having the isolationcapability, and the slice can implement the isolation capabilityrequired by the service. The control device may flexibly obtain theconfiguration data according to the isolation policy, and thereby obtainthe resource topology having a specific isolation capability.

Embodiment 2

FIG. 5 is a schematic diagram of a network scenario according toEmbodiment 2 of this application. In the scenario shown in FIG. 5 , adomain A includes a plurality of nodes, for example, R1 and R3 in FIG. 5. R1 and R3 may be edge nodes in the domain A. A domain B includes atleast one node, for example, R2 in FIG. 5 . R2 may be an edge node inthe domain B. Types of the domain A and the domain B may be the same asthose in Embodiment 1, and details are not described herein again. Acontrol device can configure nodes in the domain A and the domain B.Specifically, a first domain controller included in the control devicemay communicate with a node in the domain A, and configure the node inthe domain A. A second domain controller included in the control devicemay communicate with a node in the domain B, and configure the node inthe domain B. An orchestrator included in the control device maycommunicate with the first domain controller and the second domaincontroller. In an implementation, the first domain controller, thesecond domain controller, and the orchestrator may be independentdevices that are physically separated, and the three devices mayinteract with each other by using NETCONF. In another implementation,the first domain controller, the second domain controller, and theorchestrator may be integrated into one physical device, for example,the control device in FIG. 5 . When the first domain controller, thesecond domain controller, and the orchestrator are integrated into onephysical device, the first domain controller, the second domaincontroller, and the orchestrator may be chips or circuits on thephysical device. R1 and R2 may communicate with each other through aplurality of paths, for example, P1 and P2 in FIG. 5 . P1 and P2 areused to identify different paths. A path identified by P1 may berepresented as R1-R2. A path identified by P2 may be represented asR1-R3-R2.

A difference between the method for obtaining a network slice providedin Embodiment 2 and that in Embodiment 1 lies in that the orchestratorin Embodiment 2 may perform 301 and 308 to 310 in Embodiment 1. Theorchestrator may execute 302 in Embodiment 1 by using the first domaincontroller, and execute 303 in Embodiment 1 by using the second domaincontroller. The first domain controller may obtain first resourceinformation from a first node by performing 305. The first domaincontroller may send the first resource information to the orchestrator,or the first domain controller generates a resource topology of thedomain A by using the method in 308 and sends the resource topology ofthe domain A to the orchestrator. The second domain controller mayobtain second resource information from a second node by performing 307.The second domain controller may send the second resource information tothe orchestrator, or the second domain controller generates a resourcetopology of the domain B by using the method in 308 and sends theresource topology of the domain B to the orchestrator. The domaincontrollers may obtain a resource topology based on the resourcetopology of the domain A and the resource topology of the domain B. Forspecific content, refer to corresponding content in Embodiment 1.

FIG. 6 is a schematic structural diagram of a control device accordingto Embodiment 3 of this application. The control device provided inEmbodiment 3 is a device configured to obtain a network slice or adevice configured to obtain a resource topology. The control deviceprovided in Embodiment 3 includes a receiving unit 601, a firstobtaining unit 602, and a creation unit 603. The receiving unit 601 isconfigured to receive a slice request sent by a user, where the slicerequest includes an identifier, and the identifier is used to identifyan isolation level of a slice requested by the user. The first obtainingunit 602 is configured to obtain an isolation type of the slice based onthe identifier. The creation unit 603 is configured to create a networkslice based on the isolation type of the slice and a resource topology,where the resource topology is used to describe a network topology andisolation capabilities of N elements in the network topology, the Nelements include at least one of a node and a link, N is an integergreater than or equal to 1, and the network slice includes a node and alink that are required for implementing the slice.

In an implementation, the N elements include a first node, a secondnode, and a link between the first node and the second node; and thecontrol device further includes a second obtaining unit 604, a thirdobtaining unit 605, and a generating unit 606. The second obtaining unit604 is configured to obtain first resource information from the firstnode according to an isolation policy, where the first resourceinformation includes isolation information provided by the first nodeand a topology of the first node. The third obtaining unit 605 isconfigured to obtain second resource information from the second nodeaccording to an isolation policy, where the second resource informationincludes isolation information provided by the second node and atopology of the second node. The generating unit 606 is configured togenerate a resource topology based on the first resource information andthe second resource information, where the resource topology is used todescribe the network topology, an isolation capability of the firstnode, an isolation capability of the second node, and an isolationcapability of the link between the first node and the second node, andthe network topology is a topology between the first node and the secondnode.

When obtaining the first resource information, the second obtaining unit604 is specifically configured to: generate first configuration dataaccording to the isolation policy, where the first configuration data isused to describe the isolation capability of the first node; send thefirst configuration data to the first node; and receive the firstresource information sent by the first node, where the first resourceinformation includes the isolation information provided by the firstnode and the topology of the first node, and the topology of the firstnode is used to describe the first node and a link on which the firstnode is located. When obtaining the second resource information, thethird obtaining unit 605 is specifically configured to: generate secondconfiguration data according to the isolation policy, where the secondconfiguration data is used to describe the isolation capability of thesecond node; send the second configuration data to the second node; andreceive the second resource information sent by the second node, wherethe second resource information includes the isolation informationprovided by the second node and the topology of the second node, and thetopology of the second node is used to describe the second node and alink on which the second node is located.

When obtaining the first configuration data, the second obtaining unit604 is specifically configured to: obtain the isolation capability ofthe first node according to the isolation policy, where the isolationcapability of the first node includes isolation capabilities of thefirst node and the link on which the first node is located; andgenerate, based on the isolation capability of the first node and a datamodel, the first configuration data described by using the data model.When obtaining the second configuration data, the third obtaining unit605 is specifically configured to: obtain the isolation capability ofthe second node according to the isolation policy, where the isolationcapability of the second node includes isolation capabilities of thesecond node and the link on which the second node is located; andgenerate, based on the isolation capability of the second node and adata model, the second configuration data described by using the datamodel.

For example, the generating unit 606 is specifically configured to:determine a first isolation type based on the isolation informationprovided by the first node and the isolation information provided by thesecond node; and obtain, based on the first isolation type and thenetwork topology, a first resource topology matching the first isolationtype, where an isolation capability of a node included in the firstresource topology is the first isolation type, and an isolationcapability of a link included in the first resource topology is thefirst isolation type. After obtaining the first resource topology, thegenerating unit 606 may be further configured to obtain a secondresource topology, which specifically includes: determining a secondisolation type based on the isolation information provided by the firstnode and the isolation information provided by the second node; andobtaining, based on the second isolation type and the network topology,the second resource topology matching the second isolation type, wherean isolation capability of a node included in the second resourcetopology is the second isolation type, and an isolation capability of alink included in the second resource topology is the second isolationtype.

In an implementation, the first isolation type is fine-grained physicalisolation, coarse-grained physical isolation, or logical isolation, thesecond isolation type is fine-grained physical isolation, coarse-grainedphysical isolation, or logical isolation, and the second isolation typeis different from the first isolation type. In another implementation,the first isolation type is network isolation, link isolation, or nodeisolation, the second isolation type is network isolation, node physicalisolation, or link isolation, and the second isolation type is differentfrom the first isolation type.

For example, the creation unit 603 is specifically configured to:select, from the resource topology based on the isolation type of theslice, a sub-resource topology matching the isolation type of the slice,where an isolation capability of a node included in the sub-resourcetopology is the isolation type of the slice, and an isolation capabilityof a link included in the sub-resource topology is the isolation type ofthe slice; and store a correspondence between the sub-resource topologyand the identifier. The creation unit 603 is further configured to:obtain, based on the slice request, service information corresponding tothe slice; obtain an ingress TP and an egress TP of a third node basedon the sub-resource topology, where an isolation capability of theingress TP is an isolation capability of the slice, an isolationcapability of the egress TP is the isolation capability of the slice,the isolation capability of the ingress TP supports the isolationcapability of the node included in the sub-resource topology and theisolation capability of the link included in the sub-resource topology,and the isolation capability of the egress TP supports the isolationcapability of the node included in the sub-resource topology and theisolation capability of the link included in the sub-resource topology;and send, to the third node, a correspondence including the serviceinformation, the ingress TP, and the egress TP. The third node may bethe first node or the second node, or the third node is a node exceptthe first node and the second node.

For example, the control device can further update the generatedresource topology, and the control device further includes a fourthobtaining unit 607 and an updating unit 608. The fourth obtaining unit607 is configured to obtain updated isolation information from the firstnode, where the updated isolation information is used to describe anewly added isolation capability in the first node or an invalidisolation capability in the first node. The updating unit 608 isconfigured to obtain an updated resource topology based on the updatedisolation information and the resource topology, where the updatedresource topology is used to describe the network topology, an updatedisolation capability of the first node, the isolation capability of thesecond node, and an updated isolation capability of the link between thefirst node and the second node.

For example, the isolation level is a user level, a service level, atunnel level, a system level, a slot level, a wavelength level, a portlevel, a device level, or a network level. The isolation capability inthis embodiment of this application is an isolation function that is ofan element and that corresponds to the isolation level. The element maybe a node or a link, and may be specifically a node TP or a link TP. Theisolation information in this embodiment of this application is anisolation capability supported by a specific TP of the element. Theisolation capability supported by the TP may be represented by anisolation level in a multi-bit form, for example, in a form of the YANGmodel in the foregoing embodiment.

The units included in the control device provided in Embodiment 3 canperform corresponding functions of the control device provided inEmbodiment 1. The receiving unit 601 is configured to support thecontrol device in executing 309 in Embodiment 1. The first obtainingunit 602 is configured to support the control device in obtaining theisolation type of the slice based on the slice request in 310 inEmbodiment 1. The creation unit 603 is configured to support the controldevice in obtaining the network resource in 310 and 311 in Embodiment 1.The second obtaining unit 604 is configured to support the controldevice in generating the first configuration data in 301, 302, and 305in Embodiment 1. The third obtaining unit 605 is configured to supportthe control device in generating second configuration data in 301, 303,and 307 in Embodiment 1. The generating unit 606 is configured tosupport the control device in performing 308 in Embodiment 1.

FIG. 7 is a schematic structural diagram of a control device accordingto Embodiment 4 of this application. The control device provided inEmbodiment 4 may be the same as the control device provided inEmbodiment 3. A device structure of the control device provided inEmbodiment 4 is described from a perspective of hardware. The controldevice includes a processor 701, a memory 702, a communications bus 704,and a communications interface 703. The processor 701, the memory 702,and the communications interface 703 are connected by using thecommunications bus 704. The memory 702 is configured to store a program.The processor 701 performs, according to an executable instructionincluded in the program read from the memory 702, the method performedby the control device in the foregoing Embodiment 1. The processor 701may receive a packet or a message from a user, a first node, or a secondnode by using the communications interface 703.

When the control device has a function of the control device inEmbodiment 1, the communications interface 703 is configured to supportthe control device in performing 302, 303, 305, 307, and 309 inEmbodiment 1. The processor 701 is configured to support the controldevice in performing 301, 308, 310, and 311 in Embodiment 1. In additionto storing program code and data, the memory 702 is further configuredto cache the isolation information, the correspondence, and the resourcetopology in Embodiment 1.

FIG. 8 is a schematic structural diagram of a control device accordingto Embodiment 5 of this application. The control device provided inEmbodiment 5 may perform a corresponding function of the control deviceprovided in Embodiment 2. The control device provided in Embodiment 5includes an orchestrator 801. The orchestrator 801 is configured to:receive a slice request sent by a user, where the slice request includesan identifier, and the identifier is used to identify an isolation levelof a slice requested by the user; obtain an isolation type of the slicebased on the identifier; and create a network slice based on theisolation type of the slice and a resource topology, where the resourcetopology is used to describe a network topology and isolationcapabilities of N elements in the network topology, the N elementsinclude at least one of a node and a link, N is an integer greater thanor equal to 1, and the network slice includes a node and a link that arerequired for implementing the slice.

In an implementation, the control device further includes a first domaincontroller 802 and a second domain controller 803. The N elementsinclude a first node, a second node, and a link between the first nodeand the second node. The first domain controller 802 is configured forcommunication between the orchestrator 801 and the first node. Thesecond domain controller 803 is configured for communication between theorchestrator 801 and the second node. The orchestrator is specificallyconfigured to: obtain first resource information from the first nodeaccording to an isolation policy by using the first domain controller802, where the first resource information includes isolation informationprovided by the first node and a topology of the first node; obtainsecond resource information from the second node according to anisolation policy by using the second domain controller 803, where thesecond resource information includes isolation information provided bythe second node and a topology of the second node; and generate aresource topology based on the first resource information and the secondresource information, where the resource topology is used to describethe network topology, an isolation capability of the first node, anisolation capability of the second node, and an isolation capability ofthe link between the first node and the second node, and the networktopology is a topology between the first node and the second node.

In an implementation, the orchestrator 801 is specifically configuredto: generate first configuration data according to the isolation policy,where the first configuration data is used to describe the isolationcapability of the first node; and generate second configuration dataaccording to the isolation policy, where the second configuration datais used to describe the isolation capability of the second node. Thefirst domain controller 802 is specifically configured to: send thefirst configuration data from the orchestrator to the first node; andreceive the first resource information sent by the first node, where thefirst resource information includes the isolation information providedby the first node and the topology of the first node, and the topologyof the first node is used to describe the first node and a link on whichthe first node is located. The second domain controller 803 isspecifically configured to: send the second configuration data from theorchestrator to the second node; and receive the second resourceinformation sent by the second node, where the second resourceinformation includes the isolation information provided by the secondnode and the topology of the second node, and the topology of the secondnode is used to describe the second node and a link on which the secondnode is located.

When obtaining the first configuration data, the orchestrator 801 isspecifically configured to: obtain the isolation capability of the firstnode according to the isolation policy, where the isolation capabilityof the first node includes isolation capabilities of the first node andthe link on which the first node is located; and generate, based on theisolation capability of the first node and a data model, the firstconfiguration data described by using the data model. When obtaining thesecond configuration data, the orchestrator 801 is specificallyconfigured to: obtain the isolation capability of the second nodeaccording to the isolation policy, where the isolation capability of thesecond node includes isolation capabilities of the second node and thelink on which the second node is located; and generate, based on theisolation capability of the second node and a data model, the secondconfiguration data described by using the data model.

For example, the orchestrator 801 is specifically configured to:determine a first isolation type based on the isolation informationprovided by the first node and the isolation information provided by thesecond node; and obtain, based on the first isolation type and thenetwork topology, a first resource topology matching the first isolationtype, where an isolation capability of a node included in the firstresource topology is the first isolation type, and an isolationcapability of a link included in the first resource topology is thefirst isolation type. After obtaining the first resource topology, thegenerating unit 606 may be further configured to obtain a secondresource topology, which specifically includes: determining a secondisolation type based on the isolation information provided by the firstnode and the isolation information provided by the second node; andobtaining, based on the second isolation type and the network topology,the second resource topology matching the second isolation type, wherean isolation capability of a node included in the second resourcetopology is the second isolation type, and an isolation capability of alink included in the second resource topology is the second isolationtype.

For example, the orchestrator 801 is specifically configured to: select,from the resource topology based on the isolation type of the slice, asub-resource topology matching the isolation type of the slice, where anisolation capability of a node included in the sub-resource topology isthe isolation type of the slice, and an isolation capability of a linkincluded in the sub-resource topology is the isolation type of theslice; and store a correspondence between the sub-resource topology andthe identifier. The orchestrator 801 is further configured to: obtain,based on the slice request, service information corresponding to theslice; obtain an ingress TP and an egress TP of a third node based onthe sub-resource topology, where an isolation capability of the ingressTP is an isolation capability of the slice, an isolation capability ofthe egress TP is the isolation capability of the slice, the isolationcapability of the ingress TP supports the isolation capability of thenode included in the sub-resource topology and the isolation capabilityof the link included in the sub-resource topology, and the isolationcapability of the egress TP supports the isolation capability of thenode included in the sub-resource topology and the isolation capabilityof the link included in the sub-resource topology; and send, to thethird node, a correspondence including the service information, theingress TP, and the egress TP. The third node may be the first node orthe second node, or the third node is a node except the first node andthe second node.

For example, the control device can further update the generatedresource topology, and the orchestrator 801 is further configured to:obtain updated isolation information from the first node, where theupdated isolation information is used to describe a newly addedisolation capability in the first node or an invalid isolationcapability in the first node; and obtain an updated resource topologybased on the updated isolation information and the resource topology,where the updated resource topology is used to describe the networktopology, an updated isolation capability of the first node, theisolation capability of the second node, and an updated isolationcapability of the link between the first node and the second node.

A hardware structure of the control device provided in Embodiment 5 mayperform corresponding functions of the control device provided inEmbodiment 2. For specific functions supported by the orchestrator 801,the first domain controller 802, and the second domain controller 803,refer to corresponding content in Embodiment 2.

FIG. 9 is a schematic structural diagram of a control device accordingto Embodiment 6 of this application. An orchestrator included in thecontrol device provided in Embodiment 6 may be the same as theorchestrator included in the control device provided in Embodiment 5. Astructure of the orchestrator of the control device provided inEmbodiment 6 is described from a perspective of hardware. Theorchestrator includes a processor 901, a memory 902, a communicationsbus 904, and a communications interface 903. The processor 901, thememory 902, and the communications interface 903 are connected by usingthe communications bus 904. The memory 902 is configured to store aprogram. The processor 901 executes, according to an executableinstruction included in the program read from the memory 902, content of301, 302, 303, and 308 to 311 executed by the control device inEmbodiment 1. The processor 901 may receive a packet or a message from auser, a first node, or a second node by using the communicationsinterface 903. When the orchestrator has a function of the controldevice in Embodiment 1, the communications interface 903 is configuredto support the orchestrator in performing 302, 303, and 309 inEmbodiment 1. The processor 901 is configured to support theorchestrator in performing 301, 308, 310, and 311 in Embodiment 1. Inaddition to storing program code and data, the memory 902 is furtherconfigured to cache the isolation information, the correspondence, andthe resource topology in Embodiment 1.

FIG. 10 is a schematic structural diagram of a system used to obtain anetwork slice according to an embodiment of this application. The systemmay include a first network device, a second network device, and acontrol device. The first network device may be the first node inEmbodiment 1 or Embodiment 2. The second network device may be thesecond node in Embodiment 1 or Embodiment 2. The control device may bethe control device mentioned in any one of Embodiment 1 to Embodiment 6.For a structure of the control device, refer to corresponding content inEmbodiment 3 to Embodiment 6. For a function of the first networkdevice, refer to content related to the first node in Embodiment 1 orEmbodiment 2. For a function of the second network device, refer tocontent related to the second node in Embodiment 1 or Embodiment 2.

In the embodiments of this application, the domain A and the domain Bare used as an example for description. When it is required to obtain anetwork slice in a domain, the method provided in the embodiments ofthis application may be used: A controller or a control device of thedomain obtains, based on resource information fed back by an element inthe domain, a resource topology corresponding to the domain. Thecontroller or the control device of the domain may create, based on aslice request from a user and the method in the foregoing embodiments, anetwork slice that meets a requirement of the user. For specificcontent, refer to corresponding content in Embodiment 1 or Embodiment 2.

A general purpose processor mentioned in the embodiments of thisapplication may be a microprocessor, or the processor may be anyconventional processor. Steps of the method disclosed with reference tothe embodiments of the invention may be directly implemented by acombination of hardware and a software module in the processor. When themethod is implemented by using software, code that implements theforegoing functions may be stored in a computer-readable medium. Thecomputer-readable medium includes a computer storage medium. The storagemedium may be any available medium accessible to a computer, and mayinclude but is not limited to the following examples. Thecomputer-readable medium may be a random-access memory (RAM), aread-only memory (ROM), an electrically erasable programmable read-onlymemory (EEPROM), a compact disc read-only memory (CD-ROM) or anotheroptical disc memory, a magnetic disc storage medium or another magneticdisc storage device, or any other medium that can be configured to carryor store expected program code in an instruction or data structure formand that can be accessed by a computer. The computer-readable medium maybe a compact disc CD), a laser disc, a digital versatile disc (DVD), afloppy disc, or a Blu-ray disc.

The embodiments in this specification are all described in a progressivemanner. For same or similar parts of the embodiments, reference may bemade to each other. Each embodiment focuses on a difference from otherembodiments. Especially, a system embodiment is basically similar to amethod embodiment, and therefore is described briefly, and for relatedparts, reference may be made to some descriptions in the methodembodiment.

What is claimed is:
 1. A method for obtaining a network slice,comprising: receiving, by a control device, a slice request sent by auser, wherein the slice request comprises an identifier, and theidentifier identifies isolation information of a slice requested by theuser; and obtaining, by the control device, a network slice based on theidentifier and a resource topology, wherein the resource topologydescribes a network topology and isolation information of N elements inthe network topology, the N elements comprise a node and/or a link, N isan integer greater than or equal to 1, and the network slice comprises anode and a link that are required for implementing the slice.
 2. Themethod according to claim 1, wherein the N elements comprise a firstnode, a second node, and a link between the first node and the secondnode, and the method further comprises: obtaining, by the controldevice, first resource information from the first node according to apolicy, wherein the first resource information comprises isolationinformation provided by the first node and a topology of the first node;obtaining, by the control device, second resource information from thesecond node according to a policy, wherein the second resourceinformation comprises isolation information provided by the second nodeand a topology of the second node; and generating, by the controldevice, a resource topology based on the first resource information andthe second resource information, wherein the resource topology describesthe network topology, an isolation capability of the first node, anisolation capability of the second node, and an isolation capability ofthe link between the first node and the second node, and the networktopology is a topology between the first node and the second node. 3.The method according to claim 2, wherein the generating, by the controldevice, the resource topology based on the first resource informationand the second resource information comprises: determining, by thecontrol device, a first isolation type based on the isolationinformation provided by the first node and the isolation informationprovided by the second node; and obtaining, by the control device basedon the first isolation type and the network topology, a first resourcetopology matching the first isolation type, wherein an isolationcapability of a node comprised in the first resource topology is thefirst isolation type, and an isolation capability of a link comprised inthe first resource topology is the first isolation type.
 4. The methodaccording to claim 3, wherein the generating, by the control device, theresource topology based on the first resource information and the secondresource information further comprises: determining, by the controldevice, a second isolation type based on the isolation informationprovided by the first node and the isolation information provided by thesecond node; and obtaining, by the control device based on the secondisolation type and the network topology, a second resource topologymatching the second isolation type, wherein an isolation capability of anode comprised in the second resource topology is the second isolationtype, and an isolation capability of a link comprised in the secondresource topology is the second isolation type.
 5. The method accordingto claim 4, wherein the second isolation type is fine-grained physicalisolation, coarse-grained physical isolation, or logical isolation, andthe second isolation type is different from the first isolation type; orwherein the second isolation type is network isolation, node physicalisolation, or link isolation, and the second isolation type is differentfrom the first isolation type.
 6. The method according to claim 3,wherein the first isolation type is fine-grained physical isolation,coarse-grained physical isolation, or logical isolation; or wherein thefirst isolation type is network isolation, link isolation, or nodeisolation.
 7. The method according to claim 1, wherein the obtaining, bythe control device, a network slice based on the identifier and aresource topology comprises: selecting, by the control device from theresource topology based on the isolation information of the slice, asub-resource topology matching the isolation information of the slice,wherein an isolation capability of a node comprised in the sub-resourcetopology matches the isolation information of the slice, an isolationcapability of a link comprised in the sub-resource topology matches theisolation information of the slice, and the isolation information of theslice is determined by the identifier; and storing, by the controldevice, a correspondence between the sub-resource topology and theidentifier.
 8. The method according to claim 7, wherein the obtaining,by the control device, a network slice based on the identifier and aresource topology further comprises: obtaining, by the control devicebased on the slice request, service information corresponding to theslice; obtaining, by the control device, an ingress terminal point (TP)and an egress TP of a third node based on the sub-resource topology,wherein an isolation capability of the ingress TP matches the isolationinformation of the slice, an isolation capability of the egress TPmatches the isolation information of the slice, the isolation capabilityof the ingress TP supports the isolation capability of the nodecomprised in the sub-resource topology and the isolation capability ofthe link comprised in the sub-resource topology, and the isolationcapability of the egress TP supports the isolation capability of thenode comprised in the sub-resource topology and the isolation capabilityof the link comprised in the sub-resource topology; and sending, by thecontrol device to the third node, a correspondence comprising theservice information, the ingress TP, and the egress TP.
 9. The methodaccording to claim 7, wherein the isolation capability is an isolationfunction that is of an element and that corresponds to the isolationinformation.
 10. The method according to claim 1, wherein the isolationinformation comprises a user level, a service level, a tunnel level, asystem level, a slot level, a wavelength level, a port level, a devicelevel, or a network level.
 11. A control device, comprising: at leastone processor; and a non-transitory computer-readable storage mediumcoupled to the at least one processor and storing programminginstructions that, when executed by the at least one processor, causethe at least one processor to: receive a slice request sent by a user,wherein the slice request comprises an identifier, and the identifieridentifies isolation information of a slice requested by the user; andobtain a network slice based on the identifier and a resource topology,wherein the resource topology describes a network topology and isolationinformation of N elements in the network topology, the N elementscomprise a node and/or a link, N is an integer greater than or equal to1, and the network slice comprises a node and a link that are requiredfor implementing the slice.
 12. The control device according to claim11, wherein the N elements comprise a first node, a second node, and alink between the first node and the second node, and the programminginstructions further cause the at least one processor to: obtain firstresource information from the first node according to a policy, whereinthe first resource information comprises isolation information providedby the first node and a topology of the first node; obtain secondresource information from the second node according to a policy, whereinthe second resource information comprises isolation information providedby the second node and a topology of the second node; and generate aresource topology based on the first resource information and the secondresource information, wherein the resource topology describes thenetwork topology, an isolation capability of the first node, anisolation capability of the second node, and an isolation capability ofthe link between the first node and the second node, and the networktopology is a topology between the first node and the second node. 13.The control device according to claim 12, wherein the programminginstructions further cause the at least one processor to: determine afirst isolation type based on the isolation information provided by thefirst node and the isolation information provided by the second node;and obtaining, based on the first isolation type and the networktopology, a first resource topology matching the first isolation type,wherein an isolation capability of a node comprised in the firstresource topology is the first isolation type, and an isolationcapability of a link comprised in the first resource topology is thefirst isolation type.
 14. The control device according to claim 13,wherein the programming instructions further cause the at least oneprocessor to: determine a second isolation type based on the isolationinformation provided by the first node and the isolation informationprovided by the second node; and obtain, based on the second isolationtype and the network topology, a second resource topology matching thesecond isolation type, wherein an isolation capability of a nodecomprised in the second resource topology is the second isolation type,and an isolation capability of a link comprised in the second resourcetopology is the second isolation type.
 15. The control device accordingto claim 14, wherein the second isolation type is fine-grained physicalisolation, coarse-grained physical isolation, or logical isolation, andthe second isolation type is different from the first isolation type; orwherein the second isolation type is network isolation, node physicalisolation, or link isolation, and the second isolation type is differentfrom the first isolation type.
 16. The control device according to claim13, wherein the first isolation type is fine-grained physical isolation,coarse-grained physical isolation, or logical isolation; or wherein thefirst isolation type is network isolation, link isolation, or nodeisolation.
 17. The control device according to claim 11, wherein theprogramming instructions further cause the at least one processor to:select, from the resource topology based on the isolation information ofthe slice, a sub-resource topology matching the isolation information ofthe slice, wherein an isolation capability of a node comprised in thesub-resource topology matches the isolation information of the slice, anisolation capability of a link comprised in the sub-resource topologymatches the isolation information of the slice, and the isolationinformation of the slice is determined by the identifier; and store acorrespondence between the sub-resource topology and the identifier. 18.The control device according to claim 17, wherein the programminginstructions further cause the at least one processor to: obtain, basedon the slice request, service information corresponding to the slice;obtain an ingress terminal point (TP) and an egress TP of a third nodebased on the sub-resource topology, wherein an isolation capability ofthe ingress TP matched the isolation information of the slice, anisolation capability of the egress TP matches the isolation informationof the slice, the isolation capability of the ingress TP supports theisolation capability of the node comprised in the sub-resource topologyand the isolation capability of the link comprised in the sub-resourcetopology, and the isolation capability of the egress TP supports theisolation capability of the node comprised in the sub-resource topologyand the isolation capability of the link comprised in the sub-resourcetopology; and send, to the third node, a correspondence comprising theservice information, the ingress TP, and the egress TP.
 19. The controldevice according to claim 17, wherein the isolation capability is anisolation function that is of an element and that corresponds to theisolation information.
 20. The control device according to claim 11,wherein the isolation information is a user level, a service level, atunnel level, a system level, a slot level, a wavelength level, a portlevel, a device level, or a network level.